Vulmon
Recent Vulnerabilities
Research Posts
Trends
Blog
About
Contact
Vulmon Alerts
By Relevance
By Risk Score
By Publish Date
ibm robotic process automation vulnerabilities and exploits
(subscribe to this query)
NA
CVE-2022-46773
IBM Robotic Process Automation 21.0.0 - 21.0.7 and 23.0.0 is vulnerable to client-side validation bypass for credential pools. Invalid credential pools may be created as a result. IBM X-Force ID: 242951.
Ibm Robotic Process Automation As A Service
Ibm Robotic Process Automation For Cloud Pak 23.0.0
Ibm Robotic Process Automation For Cloud Pak
Ibm Robotic Process Automation 23.0.0
Ibm Robotic Process Automation
7.5
CVSSv2
CVE-2022-22413
IBM Robotic Process Automation 21.0.0, 21.0.1, and 21.0.2 is vulnerable to SQL injection. A remote attacker could send specially crafted SQL statements, which could allow the malicious user to view, add, modify or delete information in the back-end database. IBM X-Force ID: 22302...
Ibm Robotic Process Automation 21.0.1
Ibm Robotic Process Automation 21.0.2
Ibm Robotic Process Automation 21.0.0
NA
CVE-2022-39168
IBM Robotic Process Automation Clients are vulnerable to proxy credentials being exposed in upgrade logs. IBM X-Force ID: 235422.
Ibm Robotic Process Automation For Services 21.0.3
Ibm Robotic Process Automation For Services 21.0.4
Ibm Robotic Process Automation For Cloud Pak 21.0.4
Ibm Robotic Process Automation For Cloud Pak 21.0.3
Ibm Robotic Process Automation 21.0.4
Ibm Robotic Process Automation 21.0.3
2.1
CVSSv2
CVE-2022-33953
IBM Robotic Process Automation 21.0.1 and 21.0.2 could allow a user with psychical access to the system to obtain sensitive information due to insufficiently protected access tokens. IBM X-Force ID: 229198.
Ibm Robotic Process Automation For Cloud Pak
Ibm Robotic Process Automation
Ibm Robotic Process Automation As A Service
3.5
CVSSv2
CVE-2022-22502
IBM Robotic Process Automation 21.0.1 and 21.0.2 is vulnerable to cross-site scripting. This vulnerability allows users to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session...
Ibm Robotic Process Automation
Ibm Robotic Process Automation For Cloud Pak
Ibm Robotic Process Automation As A Service
NA
CVE-2023-25680
IBM Robotic Process Automation 21.0.1 up to and including 21.0.5 is vulnerable to insufficiently protecting credentials. Queue Provider credentials are not obfuscated while editing queue provider details. IBM X-Force ID: 247032.
Ibm Robotic Process Automation
Ibm Robotic Process Automation As A Service
Ibm Robotic Process Automation For Cloud Pak
NA
CVE-2022-22334
IBM Robotic Process Automation 21.0.0, 21.0.1, and 21.0.2 could allow a user to access information from a tenant of which they should not have access. IBM X-Force ID: 219391.
Ibm Robotic Process Automation 21.0.0
Ibm Robotic Process Automation
NA
CVE-2022-43574
"IBM Robotic Process Automation 21.0.1, 21.0.2, 21.0.3, 21.0.4, and 21.0.5 is vulnerable to incorrect permission assignment which could allow access to application configurations. IBM X-Force ID: 238679."
Ibm Robotic Process Automation
Ibm Robotic Process Automation For Cloud Pak
NA
CVE-2023-23476
IBM Robotic Process Automation 21.0.0 up to and including 21.0.7.latest is vulnerable to unauthorized access to data due to insufficient authorization validation on some API routes. IBM X-Force ID: 245425.
Ibm Robotic Process Automation
Ibm Robotic Process Automation For Cloud Pak
NA
CVE-2023-22591
IBM Robotic Process Automation 21.0.1 up to and including 21.0.7 and 23.0.0 up to and including 23.0.1 could allow a user with physical access to the system due to session tokens for not being invalidated after a password reset. IBM X-Force ID: 243710.
Ibm Robotic Process Automation As A Service
Ibm Robotic Process Automation
CVSSv2
CVSSv2
CVSSv3
VMScore
Recommendations:
NULL pointer dereference
CVE-2023-52689
CVE-2024-23803
client side
CVE-2023-52696
information disclosure
CVE-2024-35843
CVE-2024-27130
CVE-2023-52697
Vulnerability Notification Service
You don’t have to wait for vulnerability scanning results
Get Started
1
2
3
4
5
6
NEXT »